Performing Multicast Communication In Computer Networks By Using Overlay Routing

ABSTRACT

An overlay protocol and system for allowing multicast routing in the Internet to be performed at the application level. The overlay protocol uses “native” Internet multicast and multicast routing protocols to route information, according to overlay routing tables. Overlay groups are mapped to native multicast groups to exploit native multicasting in regional or local forwarding domains. Use of the overlay protocol allows overlay distribution to be handled in a more intelligent and bandwidth-managed fashion. Overlay routers are placed at each of several local area networks, Internet service provider&#39;s point of presence, enterprise, or other cohesively-managed locations. The overlay computers are configured according to bandwidth and security policies, and perform application-level multicast distribution across the otherwise disjoint multicast networks by using the overlay routing. The result is an overlay multicast network that is effectively managed according to local network management policies. Application-level control can be applied to the transferred data at the overlay routers.

CROSS-REFERENCE TO RELATED APPLICATIONS; BENEFIT CLAIM

This application claims benefit of priority under 35 U.S.C. §120 asContinuation of U.S. patent application Ser. No. 12/426,185, now U.S.Pat. No. 8,370,522, filed Apr. 17, 2009, the entire contents of which ishereby incorporated by reference as if fully set forth herein. Theapplicant(s) hereby rescind any disclaimer of claim scope in the parentapplication(s) or the prosecution history thereof and advise the USPTOthat the claims in this application may be broader than any claim in theparent application(s).

U.S. patent application Ser. No. 12/426,185 is a continuation of U.S.patent application Ser. No. 11/544,792, filed Oct. 5, 2006, which is acontinuation of U.S. patent application Ser. No. 10/600,142 filed Jun.19, 2003, now U.S. Pat. No. 7,133,928, which is a continuation of U.S.patent application Ser. No. 09/323,869 filed Jun. 1, 1999, now U.S. Pat.No. 6,611,872, which claims the benefit of priority from U.S.Provisional Application Ser. No. 60/115,454, filed Jan. 11, 1999, thecontents of each of which is incorporated herein by reference in itsentirety for all purposes as if fully set forth herein. This applicationis related to the following patent applications and/or provisionalapplications which are hereby incorporated by reference as if set forthin full in this specification: U.S. Provisional Patent application Ser.No. 60/137,160, entitled “SYSTEM FOR BANDWIDTH ALLOCATION IN A COMPUTERNETWORK” filed on Jun. 1, 1999; and U.S. Provisional Patent applicationSer. No. 60/137,153 entitled “SYSTEM FOR MULTIPOINT INFRASTRUCTURETRANSPORT IN A COMPUTER NETWORK” filed on Jun. 1, 1999.

BACKGROUND

As the Internet gains in popularity it is desirable to allow broadcastsof live media, such as a television program or radio program, over theInternet. However, a problem with such “streaming media” broadcasts isthat they require very high data transfer rates across many servers,routers and local area networks that form the Internet. Because of this,high-quality, scalable broadcasts, or “multicasts,” of streaming mediainformation to massive numbers of end-users at once over the Internethave not been achieved to date.

Examples of attempts to design and. deploy multicast systems for theInternet include systems by RealNetworks and Broadcast.com. RealNetworkshas built an Internet broadcast infrastructure called the Real BroadcastNetwork (RBN) while Broadcast.com has partnered with Internet ServiceProviders (ISPs) and content providers to build a broadcast system basedon native Internet multicast routing. A typical streaming broadcastconsists of a server that unicasts a User Datagram Protocol (UDP) flowto each requesting client. Bandwidth is managed very crudely by simplylimiting the number of simultaneous active flows via some simpleconfiguration hook at the server. While this approach works for today'sdemands, it wastes network bandwidth and cannot scale to very largeaudiences anticipated in the future.

Although some existing products (like NetShow and Cisco's IP/TV) supportmulticast, Internet Service Providers (ISPs) and enterprise networkmanagers have been slow to adopt multicast because it is difficult toconfigure, manage, and debug. For some companies, these deploymentproblems are crucial barriers because they view multicast as criticalfor their long-term viability and feel that failure to successfullyintegrate multicast could compromise their mission.

A successful Internet broadcast system depends on its ability tobroadcast audio and video programming to a large number of simultaneoususers. Two approaches for broadcasting streaming media are replicatedunicast (one user per stream) and multicasting (multiple users perstream).

While unicast delivery has enjoyed tremendous success as the fundamentalbuilding block of the Internet, multicast has proven far more complexand many technical barriers remain that prevent multicast from beingdeployed across the wide area. Despite a decade of research anddevelopment, interdomain multicast routing has yet to be successfullyrealized and there are many reasons to believe that multicast, in itspresent form, may never be universally deployed throughout the Internet.In this case, applications that assume ubiquitous multicast connectivityto attain scalable performance will never become feasible. On the otherhand, multicast, when restricted to a singly administered networkdomain, has been much easier to configure and manage, and for thisreason, has been a resounding success in isolated deployments. That is,it's easy to build an isolated multicast “cloud” as long as it doesn'tspan multiple administrative domains and involve highly heterogeneousequipment with different multicast implementations.

While uniform and homogeneous multicast clouds can effectively carrymulticast traffic that is isolated to LANs or autonomous corporatenetworks, a wide range of compelling applications, such as streamingmedia broadcasts, are potentially enabled by interconnecting theisolated multicast clouds into a very large-scale distribution network.However, attempts to use wide area multicast routing protocols to solvethis problem have failed. Another problem with interconnecting multicastclouds has been lack of control over the multicast traffic from domainto domain. This implicates not only bandwidth considerations, butsecurity issues as well.

Thus it is desirable to complement and enhance the vast array ofexisting servers and end-clients with a state-of-the-art system thatprovides an improved network infrastructure for achieving multicastingof information. Such a system should enhance existing digitalaudio/video/media applications and enable them to work more effectivelyat large scale and across heterogeneous environments. The system shouldprovide flexible bandwidth management and diagnostic tools to networkmanagers such as by providing localized control over traffic and contentof multicast data. The system should make use of existing, widelydeployed communication protocols and procedures to achieve efficienttransfer of information.

SUMMARY OF THE INVENTION

The present invention is to be embodied in a commercial product byFastForward Networks, called “MediaBridge.” Each MediaBridge is aprocess that is executed on a computer, or other processor or processingdevice, connected to a network. Multiple MediaBridges transfer datausing an “overlay” network. In a preferred Internet embodiment, theoverlay protocol uses “native” Internet protocols to route information,according to overlay routing tables, between otherwise disjoint andisolated multicast clouds. This allows the overlay distribution to behandled in a more intelligent and bandwidth-managed fashion. Forexample, MediaBridges are placed at each of several local area networks(LANs), ISP “point of presence” (POP), enterprise, or othercohesively-managed locations. The MediaBridges are configured accordingto bandwidth and security policies, and perform application-levelmulticast distribution across the Network Access Points (NAPs) usingoverlay routing. The result is an overlay multicast network that iseffectively managed according to traffic policies defined locally ateach NAP.

The present invention allows application-level control to be applied tothe transferred data. For example, if a confluence of high-bandwidthvideo flows arrives at a choke point in the network (where the chokepoint is either a physical bandwidth limit or an administrativelyconfigured bandwidth constraint), the MediaBridge intelligently filtersand/or transforms flows so that they fit onto the outgoing link. Thetransformations can, for example, reduce the frame rate or resolutionuniformly as opposed to simply dropping packets at the network layer(without accounting for media semantics). The invention exploitsapplication-level activity to control adaptation. For example, in avideoconference, cues from the audio channel, or from the dispositionsof the user interfaces at the clients, can be used to decide to dedicatemore of the traffic class' bandwidth allocation to the current speaker.

An end-user client application can attach to the overlay network usingeither unicast or multicast communication between it and a MediaBridgeon the overlay. Thus, a web page can have a simple “point and click”hyperlink to initiate reception of a multicast audio/video productionwhere a channel ID is embedded in the Uniform Resource Locator (URL). Ora user can send a channel ID, or other identification, to a MediaBridgeto subscribe to a program multicast.

In one embodiment of the invention an overlay routing processor fortransferring information over a computer network is disclosed. Thecomputer network has a native routing protocol. The overlay routingprocessor includes instructions for associating computers on the networkwith a given overlay group; instructions for determining whetherreceived information is associated with the given overlay group; andinstructions for routing the received information to the computersassociated with the given overlay group by using the native routingprotocol.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows overlay router arrangements;

FIG. 2 illustrates the Overlay Multicast Network Architecture;

FIG. 3A shows a computer suitable for use with the present invention;FIG. 3B show subsystems in the computer of FIG. 3A; FIG. 3C illustratesa network configuration;

FIG. 4A shows a unicast-initiated overlay routing step;

FIG. 4B illustrates a second step in overlay routing;

FIG. 4C illustrates a third step in overlay routing;

FIG. 5 illustrates a second approach to unicast-initiated overlayrouting; and

FIG. 6 illustrates details of header and address processing in thepresent invention.

DESCRIPTION OF THE SPECIFIC EMBODIMENTS

The present invention implements “overlay” multicasting. So-calledbecause some of the routing processing by MediaBridge's uses a routingscheme that is independent of, in addition to, and at a higher levelthan the prior art “native” scheme. With the approach of the presentinvention, any of the current multicasting techniques, such as DVMRP,PIM, CBT, etc. are referred to as “native” multicasting, or “nativeprotocols.”

The invention uses native multicast only as a forwarding optimizationwhere it is locally viable—typically within medium-scale,singly-administered, homogeneous network domains. In this model, thenetwork consists of a set of isolated native multicast clouds upon whicha virtual network of application-level routing agents called “overlayrouters”. The overlay routers (i.e., the MediaBridge computers)implement multicast routing protocol that makes use of sophisticatedapplication-level knowledge and management infrastructure. Unicastclients can connect directly to overlay routers via unicast so thatregions of the network that do not provide native multicast support canbe reached. Unlike existing multicast technologies, this allows clientsto connect to overlay routers using unicast UDP or TCP through aredirection and location service. This allows clients that are notdirectly attached to a multicast capable network to communicate andreceive transmissions from the overlay network.

Moving wide-area multicast routing out of the network layer and up tothe application layer, affords number of advantages:

-   -   Simplicity. The overall multicast routing problem is simplified        because it is decomposed into two separable and individually        tractable sub-problems: (1) the configuration of native        multicast routers in a singly administered network domain        and (2) the configuration .of overlay routers to interconnect        the disparate regional networks and tightly manage the bandwidth        consumed by multicast across these domains.    -   Rich Management. Because routing is carried out at the        application layer, we can implement well-defined policies that        reflect application priorities and provide high-level services        such as billing. Routers are no longer hidden by a thick        protocol layer that hides application knowledge. Instead, the        overlay routers can be configured more like servers and        bandwidth managed and apportioned intelligently across different        application classes.    -   Efficient Rendezvous. Application-level knowledge vastly        simplifies the problem of rendezvous. Because different        applications naturally have different models for how the        distributed components might interact or at what scale and        directionality they interact, the rendezvous mechanism can be        optimized by exploiting application requirements. For example, a        streaming video server might best be contacted by querying the        content provider's ordering service or by contacting the        corporate headquarters' web page. Alternatively, a        videoconference might best be initiated by contacting an H323        Multi-point control unit (MCU) that is near the physical        conference room of the hosting site.

The invention is next discussed by first presenting the generalarchitecture of the overlay multicast network approach. Next, detailedexamples of transaction steps using the architecture are described.

The Overlay Multicast Network Architecture 1. Introduction

This section describes the overlay multicast network (OMN) architectureof the present invention.

The OMN architecture utilizes a two-level addressing strategy, whereoverlay addresses are carried in an additional overlay header (whichappears after the 30 UDP header), but before the user's UDP payload, andnative multicast addresses are. computed from overlay addresses using anovel hashing scheme that exploits multicast address scopes. To properlyroute traffic across the overlay network, overlay routers implement amulticast routing protocol that is, in some ways, analagous to BGMP andBGP. In addition, unicast clients can connect directly to overlayrouters via UDP so that regions of the network that do not providenative multicast support can be reached. The overlay routers operate atthe application-level. This allows the overlay routers to be easilyextended with application-level knowledge to carry outsemantically-aware transformations conditioned on bandwidth constraintsspecified by external policies.

The OMN architecture includes a number of core elements:

-   -   a forwarding and routing framework for computing multicast        distribution tree across the virtual overlay network,    -   a multipoint reliable transport protocol for disseminating data        reliably into and across the overlay network,    -   a plugin framework for extending overlay routers with new        application-level knowledge,    -   a bandwidth scheduling framework for scheduling traffic classes        according to hierarchical link-sharing policies,    -   a method for communicating between plugins and the bandwidth        management subsystem to effect application-level adaptation from        within the network, and    -   a referral directory service that redirects end hosts to the        closest overlay router:

This application is principally concerned with the routing components of20 the OMN architecture and the relationship among the differentsubsystems. Other related applications include those referenced at thebeginning of this specification.

2. The Network Model

The network model assumed by an overlay network is a collection ofisolated (but possibly overlapping) regions of native multicastconnectivity. Overlay routers are deployed across this arrangement ofmulticast clouds and peer with each other either via unicast ormulticast UDP/IP to form a network of application-aware multicastforwarding agents. End hosts inject traffic into the overlay networkusing either native multicast across a “leaf scope” or using unicastcommunication directly to a nearby overlay router.

Even though the OMN framework operates at the application layer, overlayrouters must compute what amounts to network-level routes to determinehow to flood multicast flows across and throughout the appropriateregion of the overlay network. Thus, in the OMN architecture routingoccurs at two layers, the network layer and the application layer.Because routing is carried out. the application layer, application-levelknowledge can be integrated into the forwarding process to transformpacket flows at points of administrative discontinuity.

In this two-layer routing model, the network (IP) source and destinationaddresses are rewritten on each overlay router hop, which means thatcertain structure and state (like address allocations and multicastspanning trees) need not be globally consistent across multicastdomains. Note that this allows overlay routing without requiring allrouters in the network to be upgraded to recognize and forward a newpacket type. No change to the existing routing infrastructure is neededbecause of the two-layer addressing scheme. That is, existing multicastrouters can remain intact while new overlay routers are installed at theborders of administrative boundaries, or domains. We thus exploitexisting native multicast routing technology within administrativedomains and across transit domains when and where available.

2.1 The Overlay Multicast Service Model

In contrast to native IP Multicast, the overlay multicast service modeltransforms packets as necessary in order to forward application-levelflows in a bandwidth-managed fashion. In this model, an application mayinject a flow into the network without concern that it will congest thenetwork since the overlay routers will thin the stream as necessary inchoke points in the network and ensure that all policy-defined bandwidthconstraints are adhered to. In addition, sources must explicitly signalto the network their intention to send and optionally indicate typeinformation describing their traffic. Administrative policies can beconfigured into the infrastructure. These policies can permit orrestrict sources from sending based on rich, application-level policies.

To maximize the congruence between the OMN architecture and the existentIP Multicast service interface, hosts use the standard IP Multicastinterface to 30 inject data packets into and receive packets from anOMN. In one embodiment of the invention, overlay multicast senders (orproxies for the sender) explicitly signal to the network their intentionto transmit. This is unlike IP multicast, where hosts may simply sendpackets addressed to a Class D multicast group without any explicitsignaling. As part of this dialogue, the sender describes the channelthat it intends to use (e.g., UDP multicast, UDP unicast, or TCP), and,once negotiated, overlay-enabled multicast packets may be sent into thenetwork. This sender setup process may fail if the source does not haveadministrative permission to send. Thus, OMN sources can be tightlycontrolled in contrast to normal IP multicast, which provides no controlover senders.

To invoke application-level processing and management capabilitieswithin the OMN network infrastructure, an OMN sender (or proxy thereof)may signal application knowledge into the network using a multipointdata dissemination framework. In the preferred embodiment, thisframework uses a protocol known as Multipoint Infrastructure Transport(MINT) Protocol. MINT provides a group-oriented, reliable deliverymechanism between a nodes in the OMN and is described in detail in aco-pending patent application referenced at the beginning of thisspecification.

Using MINT, senders can attach named values to an overlay multicastgroup which is published into and across the overlay network, allowingother group members as well as network entities to query this “database”of state. Each tuple in the database, called a “mint”, is identified byits owner (the OMN sender) and name (and implicitly the group). Thetuples are disseminated reliably to all parts of the network with activeparticipants. Note that given tuples need to flow only to overlayrouters that fall along a path from the source to the set of activereceivers for that group. An end host may query the OMN subsystem todiscover and/or enumerate all known owners and all known keys publishedby each owner. In turn, the values can be queried by name/owner, and theapplication can be asynchronously notified when the owner modifies thevalue.

Certain mints are reserved for system specific functions that, forinstance, map an overlay group to an application type or describe theattributes of an overlay group so that it can be mapped into locallydefined traffic classes in different parts of the network. For flowsthat require application-level processing and/or traffic management, aspecial “setup mint” provides the requisite information and must precedethe transmission of data. Packets are dropped by the overlay network ifthe setup mint is not present, including the time during which the setupmint is in transit.

2.2 Virtual Interfaces

A fundamental communication construct in overlay multicasting is a pathabstraction called a “virtual link”, which joins together an overlayrouter with other overlay routers and with end hosts. The (virtual)attachment abstraction of a link to an overlay router is called avirtual interface or VIF. There are three primary classes of VIF: atransit VIF (TVIF) interconnects two or more overlay routers in apeering relationship, a leaf VIF (LVIF) interconnects end hosts withnative multicast connectivity to the overlay network, and a unicast bankVIF (UVIF) interconnects end hosts without multicast access via unicastto a “nearby” overlay router.

Applications send and receive OMN packets through an overlay router thatmanages the LVIF. The overlay router transforms each native multicastpacket into an overlay packet by encapsulating it in an overlay header,which is situated between the UDP header and application payload. Thisoverlay header includes the destination overlay group, which consists ofa 32-bit rendezvous point (RP) identifier and a 32-bit channel number.When a packet reaches its destination LVIF, the last-hop overlay routerstrips off the overlay header and forwards the packet to the end host(or set of end hosts) using unicast (or multicast) UDP.

Each transit VIF represents a link in the overlay network topology andoverlay routers forward packets to each other over these virtual paths.A collection of overlay routers can peer with one another as a groupover a “multicast transit VIF”. Overlay routers can peer with each otherdirectly in a “point-to-point” configuration using a “unicast transitVIF”. In addition, end-hosts inject/receive packets from the overlaynetwork by either (1) transmitting packets into a leaf VIF using nativemulticast or (2) transmitting packets directly to an overlay routerusing unicast UDP. For the latter case, the address of a nearby overlayrouter can be queried using a directory service.

An example of overlay routing is shown in FIG. 1. FIG. 1 shows overlayrouters (ORs) arranged to handle traffic in a transit domain usingnative multicast, and in a point-of-presence system between a nativerouter (R) and remote, access concentrator (RAC). Many such arrangementsof overlay routers are possible. The number, placement and physicalconnection of overlay routers is a design tradeoff with respect todesired efficiency, cost and features as is practicable.

2.2.1 Overlay Scope

When an overlay router sends an overlay packet out a VIF, it mustdetermine the network-layer address of the “next hop”. If the VIF iscomposed of only a single peer, then the address is simply the unicastaddress of that peer. But, for a collection of peers, the overlay routermust map the overlay group into a native multicast group so that thepeers can receive the traffic efficiently using native multicast. Toprovide controls over transit traffic containment, this address ischosen from a range of administratively scoped addresses, which areconfigured into the overlay router when the peering relationship isestablished. This scope is referred to as an overlay scope in the OMNarchitecture.

The native IP multicast service supports two type of “scoping”abstractions: hop-based scope and administrative scope. In hop-basedscope, the time-tolive (TTL) field in the IP packet header constrainsthe distribution of a packet. Because the TTL limits the number offorwarding hops that a packet can sustain before being dropped, thesource host can constrain the reach of the packet by setting the TTLfield to an appropriate value. In administrative scope, routingboundaries are configured borders between scopes (e.g., between separateorganizations). A routing boundary is represented by a range ofmulticast addresses, i.e., an administrative boundary is imposed bypreventing multicast packets that fall within the administrative addressrange to be blocked at that boundary point. A special block of multicastaddresses is reserved for administrative scope (239.0.0.0 to239.255.255.255) and since administratively scoped traffic does not flowacross boundaries, scoped addresses need not be unique acrossorganizational boundaries.

Associated with each VIF is a rule by which overlay multicast addressesare mapped onto the overlay scope, or range of native multicastaddresses. An overlay scope is expressed as an IP4 Class D address and aprefix length, e.g., 249.2/16 represents the block of addresses from249.2.0.0 to 249.2.255.255. An algorithm to deterministically map anoverlay multicast address into an address in an arbitrary overlay scopecan be easily constructed using well-known hashing techniques.

2.2.2 Leaf VIFs

Multicast traffic enters and leaves the overlay network through aspecial VIF called a “leaf VIF” (LVIF) (so called because these VIFs aresituated at the leaves of the multipoint overlay distribution tree).FIG. 2 is an illustration of overlay routers arranged in leaf andtransit domains. To contain and control traffic within the LVIF, aTTL-based multicast scope is imposed at the desired boundary of theleaf. That is, to create an LVIF, a network administrator determineswhich subnets in the network should comprise that LVIF, and in turn,configures each router attached to those subnets with an appropriate TTLthreshold. In turn, applications and overlay routers inject traffic intothe LVIF with a TTL less than the threshold thereby containing the reachof raw multicast traffic as desired.

Unfortunately, TTL scopes can lead to inefficient use of bandwidthbecause TTL-scoped traffic often cannot be “pruned” off subnets thathave no interested receivers. To-remedy this, administrative scopeboundaries can be placed precisely along the border of the leaf scope inquestion. If applications then use addresses from these ranges, thetraffic is consequently scoped and pruned off subnets (within the leaf)for which there are no receivers. However, because the overlay networkeffectively bridges spatially distinct multicast sub-regions, the usuallocality implied by administrative scopes no longer applies. Thus, suchscopes must be carefully used and set aside for use only for the overlaynetwork (i.e., not relied upon for other uses of scoped traffic sincethe overlay network deliberately leaks this traffic outside the region).Another problem with administrative scopes is that different sites mightchoose different address ranges for scopes. Thus, the overlay multicastarchitecture reserves a special range of administratively scopedaddresses to be used exclusively for the-purpose of imposing boundarieson leaf VIFs.

Given that the LVIF scoping abstraction is in place to constrain thereach of data traffic, end hosts and overlay routers still must exchangecontrol traffic in order to determine which traffic to forward into andout of the LVIF. That is, the overlay router at the edge of the domainmust somehow determine the set of multicast groups that it must listento in order to receive traffic from active senders. Likewise, it mustdetermine whether receivers are present for any overlay group inquestion so that it can join the corresponding group across the overlaynetwork (see the Section 4 below) and forward the consequent trafficfrom sources in other remote LVIFs into the local LVIF. To solve theseproblems, end systems and overlay routers utilize control protocols thatrun over well-known multicast groups and TCP to carry out the necessarystate exchanges. Receiver overlay group membership is reflected tooverlay routers through a protocol called the Domain-wide GroupMembership Protocol (DGMP). The presence of senders for a given overlaygroup is signaled though the Overlay Sender Setup Protocol (SSP). Inturn, senders use MINT to further attach attributes to their flows toeffect application-level processing and bandwidth management of theirtraffic within and across the overlay network.

To enhance fault tolerance and improve routing performance, multipleoverlay routers may be attached to a single LVIF. When multiple overlayrouters are incident to an LVIF, they intercommunicate with each otherto elect a designated router (DR) for the LVIF. The remaining overlayrouters are demoted to subordinate status. As such, only the DR injectsor extracts traffic from the LVIF, while the subordinate routers act asbackups in case the DR goes down. In addition, the subordinate routersmay peer with the DR using the normal peering relationships (see below),which improves the routing performance by potentially reducing the pathlengths from a given LVIF that may be connected to multiple externalnetworks.

In short, to receive or send packets into an OMN Network, end hostsexplicitly register their intention to do so by using a combination ofprotocols that run across the LVIF.

LVIF Receivers

The receiver group membership protocols are relatively straightforwardcompared to the sender setup process. Unlike senders, which mustdescribe their flow attributes, receivers simply announce their interestfor a particular group to the overlay routers in the LVIF using DGMP,which is a standard protocol based on the Interdomain Multicast Routing(IDMR) Working Group's protocol for “Domain Wide Multicast GroupMembership Reports”. Like this related work, DGMP resembles the InternetGroup Management Protocol (IGMP), but rather than run on isolated LANs,it runs across the LVIF. In this scheme, one or more overlay routers areattached to an LVIF and exchange messages over a well-known multicastgroup (the “DGMP channel”). A distributed election algorithm chooses oneoverlay router to be the designated router. This router, in turn,solicits membership reports by multicasting a “query” packet on the DGMPchannel. All end hosts then announce their interest in all groups theywish to receive by multicasting “report” packets on the same DGMPchannel. DGMP, unlike IGMP, does not suppress duplicate report packets,which means that the overlay router and/or monitoring systems running inthe LVIF can learn of all active multicast receivers (e.g., foraccounting or diagnostics). To avoid traffic transients induced bysynchronized feedback, end hosts wait a random amount of time beforegenerating their report packet (such that report traffic is spreadadequately across the reporting interval). Since the overlay routercontrols the query rate, control bandwidth overhead can be easily tradedoff for membership accuracy through adjustments made only to theinfrastructure (i.e., the overlay router).

To support unmodified multicast clients, a third-party end system mayact as a proxy for another host. That is, an IP host may respond to DGMPqueries on behalf of another. With this proxy capability, an agent canbe built that passively monitors IGMP messages on a LAN, converts theClass D multicast addresses carried in the IGMP packets to overlaygroups, and relays this overlay group information onto the DGMP channel.If this agent is placed on each LAN within an LVIF, then no changes areneeded to support the receive path of conventional, unmodified multicastapplications. That is, the agent notices whenever a receiver in itsattached LAN joins a multicast group and relays the appropriate overlaygroup membership messages on the LVIF-wide DGMP channel. Note that underthis scheme, when a proxied application exits, the IGMP reports cease,which automatically prevents further generation of DGMP messages.

Once the DR learns that receivers for a given group exist in itsincident LVIF, it informs the routing subsystem which causes packetsaddressed to that group to be delivered from anywhere in the overlaynetwork. When a packet addressed to that group arrives at the DR, thepacket is forwarded onto the LVIF using UDP. At this point, the overlayheader is removed and the packet is addressed to the UDP port indicatedin said header.

Unicast Receivers

In many cases, multicast connectivity will not reach everywhere and manyclients may want to connect to the overlay network without the aid ofmulticast. In this case, a receiver interacts directly with an overlayrouter with unicast communication. The receiver consults a well-knowndirectory service to provide the IP address of an overlay router. Inturn, it sends control information indicating the overlay group desiredand the transport connection parameters that the overlay router shoulduse to forward that group's traffic (e.g., IJDP or TCP port numbers). Inaddition, the client can provide the overlay router with additionalapplication-level information that will allow it to optimize thedelivery of traffic to that destination. For example, the client'sInternet access bandwidth could be included so that the overlay routercan deliver a version of the overlay multicast traffic signal that willadhere to this bandwidth constraint and thus not congest the network.

Clients do not have to contact the directory service directly. Forexample, existing clients can be made to join the overlay group as aside effect of clicking on a web link (as discussed below).

LVIF Senders

In IP Multicast, senders simply transmit packets, to a group addresswithout invoking any sort of control protocol like IGMP. In turn,routers directly attached to the local subnet simply detect thesemulticast packets and forward and route them accordingly. However, thisis not easily done at the application layer since an overlay router mustexplicitly join the native group in question in order to receivepackets. Thus, the OMN architecture requires an analog protocol to DGMPfor signaling the presence of sources within the LVIF to the attachedoverlay routers so that they can join and leave native groups asrequired. Additionally, the application-aware nature. of the OMNinfrastructure requires that source describe the characteristics andbehavior of their flows. Since this state needs to be signaled reliablyinto the network, an end host requires a reliable transport protocolbetween it and its nearby overlay router to transmit this state. Ratherthan implement one protocol, modeled say after DGMP, for signaling thepresence of senders and another that provides a reliable delivery modelfor transferring flow state to the overlay router, these two functionsare merged into a single protocol, the Overlay Sender Setup Protocol(SSP), which in turn leverages TCP to provide reliability. Using SSP, asender (or proxy thereof) informs the DR of the overlay group and UDPport that it uses to carry its traffic. This allows the DR to join thegroup in question and relay said traffic from the indicated UDPmulticast group and port into the overlay network. To effect theexchange of control state, the sender establishes an SSP connection withthe DR, which is determined or discovered with a or resource discoveryprotocol.

SSP also provides the interface for senders to publish data into theoverlay network via MINT. Mints are injected into the network using asimple protocol layered on top of the SSP channel. That is, SSP providesthe conduit both for senders (or proxies) to signal their intention tosend to a given overlay group and for senders to publish reliablydisseminated mints into the overlay network. To support unmodified,native multicast clients, a third party agent (which we call a shim) mayperform the SSP and MINT signaling functions on behalf of the unmodifiedclient or server.

Once a setup binding is signaled into the network via SSP, the state isrefreshed to persist; otherwise, the DR assumes the sender is no longerpresent and tears down the corresponding state. This can occur directlywithin SSP via explicit refresh messages, or it can be refreshedindirectly as a side effect of the sender generating data packets. Thatis, if the sender is continually active, there is no need to maintainthe SSP connection (e.g., a streaming video server that plays out a livebroadcast). Otherwise, if the sender is “bursty” (i.e., alternatesbetween active and idle periods), the sender state must be maintained byleaving the SSP connection in place (and relying upon SSP keepalives tomaintain the connection). One disadvantage of the data-driven approach,however, is that if the DR crashes, the binding must be re-establishedwhen the DR resumes or when another DR takes over.

Before the network will forward a traffic for a particular overlaygroup, some source in the network must publish a special,system-reserved flow descriptor mint for that group, which describes themedia type of the flow and provides descriptive information that allowsoverlay routers to map a flow onto a locally-defined traffic class.This, in turn, allows overlay routers to perform application-specificprocessing and traffic management. If the flow does not need to beexplicit managed or processed by the OMN infrastructure, then a flowdescriptor indicated such (i.e., a best effort descriptor) must still bepublished into the network. Packets are dropped by the OMN until theflow descriptor is disseminated properly.

It is an error for multiple flow descriptors to be published into thenetwork for a single overlay group from different sources. If thisoccurs, conflict resolution heuristics are invoked, but the results areundefined. The error condition is detected and propagated to the overlaynetwork management facilities to be fed back to the user or userscausing the problem and/or to a network operator.

Unicast Senders

In many cases, multicast connectivity will not reach everywhere and manyclients may want to connect to the overlay network without the aid ofmulticast. In this case, a sender interacts directly with an overlayrouter with unicast communication to transmit traffic into the overlaymulticast network. The sender consults a well-known directory service toprovide the IP address of an overlay router at the edge of the OMNnetwork. In another configuration, the sender can be staticallyconfigured with the address of a nearby overlay router. The sender sendscontrol information indicating the overlay group that is to be used andapplication-level information that describes the contents of thetransmission. In addition, the sender publishes arbitrary flowdescription information, disseminated via MINT, which can be used bytraffic management policies within the network infrastructure. Toinitiate communication, the sender and overly router allocate andexchange transport connection parameters (e.g., UDP or TCP port numbers)that the overlay router then uses to receive that group's traffic. Oncethis connection is established, the sender can inject traffic into theoverlay network using unicast.

2.2.3 Transit VIFs

Once a packet has been successfully delivered to an overlay routereither across an LVIF via multicast or via direct unicast communication,it is propagated to all other LVIFs and unicast receivers in the overlaynetwork that include members interested in receiving traffic sent to theoverlay group in question. To accomplish this, the first-hop overlayrouter prepends an overlay packet header on the UDP payload and forwardsthe traffic to peer overlay routers according to multicast “routes” thatspan transit virtual link interfaces (TVIF). Overlay routers forward thepacket based on the overlay group stored in the overlay header. Ineffect, a TVIF provides a virtual interconnection between virtuallyadjacent overlay routers.

Two or more overlay routers peer with each other across a TVIF using twotypes of communication channels:

-   -   a bi-directional TCP connection to exchange control messages        (i.e., routing messages and group membership state), and    -   a unidirectional, connectionless UDP channel to forward data        packets.

We refer to these two abstractions as the control channel and datachannel respectively.

The data channel may be either unicast (called a TVIF) or multicast(called 30 a multicast TVIF), and in either case, packets are framedover UDP. In the unicast case, packets are simply transmitted to theadjacent peer using that peer's IP address and a well-known UDP port.That peer, in turn, receives the packet on the expected UDP port andinspects the overlay header to determine where to route the packet next,and so forth.

The Multicast TVIF

The multicast case is more complex and interesting. Here, a collectionof overlay routers peer with each other using native multicast runningacross a single TVIF. In this case, the communication abstraction isisomorphic to a fully-connected mesh of overlay routers but with theefficiency of multicast. The control channels are effected using afully-connected mesh of TCP connections, while the pairwise virtual datachannels are effected using a single native multicast group. To isolatethis multicast traffic to a well-confined region, peer routers may beplaced in an overlay scope, where either or both administrative and TTLscope boundaries limit the reach of data traffic. This scope defines aspecific segment of the overlay network and peer routers forward overlaypackets to each other by embedding them in native multicast datagrams.To effect this, overlay routers map overlay addresses onto native groupaddress using a well-defined hash function and the peers that areinterested in receiving a certain overlay group join the correspondingnative group at the network layer. In this fashion, overlay routersexploit native multicast routers across the transit regions in anefficient manner.

For example, suppose there are three routers A, B, and C, and overlaygroups G1 and G2. Further suppose that the spanning tree for group G1 isincident to A and B and the spanning tree for G2 is incident to allthree routers. Then, A and B would join group G1 where A, B, and C wouldall join group G2. Thus, when A sends packets to G1, they are sent onlyto B, and when anyone sends packets to G2, they are sent to everyone inthis set.

However, overlay routers cannot natively join an overlay group. Instead,they hash the overlay group to a native group, where the hash functionis chosen to map the entire overlay address range into the nativemulticast address range that is bound to the overlay scope of themulticast TVIF. Call the hash function that performs this mapping “ho.”Thus, when an overlay router learns that it is incident to the multicastrouting tree for some overlay group G with respect to a particularmulticast TVIF, it joins the native multicast group h(G). In turn, anypeer routers that forward packets for group G on that TVIF, will sendthe packet to group h(G) and the router in question will consequentlyreceive the desired traffic. For example, A and B would exchange packetsby joining and sending packets to group h(G1), whereas A, B; and C wouldeach join group h(G2) and forward packets to each other over that nativegroup. Note that each TVIF may have an h(.) that depends on the overlayscope used to define that TVIF.

Moreover, the overlay scope can configured with an arbitrary addressrange so that multiple multicast TVIFs can overlap in non-trivial andinteresting ways. Thus, a single router can be virtually attached tomultiple, isolated multicast scopes and forward traffic among them.

For example, in the above scenario, A, B, and C form one TVIF, while C,D, and E might form another. In this case, if we ensure that themulticast address ranges for the overlay scopes that define two TVIFsare disjoint, then C can efficiently forward traffic between the tworegions. In effect, two hash functions, say hl and h2, would map overlaygroups to native groups in the two TVIFs. Thus, C would forward a packetaddressed for overlay group G from the first TVIF to the second TVIF byreceiving packets sent to the native group hl (G) and forwarding thosepackets to the native group h2(G). (As explained later, the overlayrouter performs several important checks to ensure that the traffic isreceived in congruence with the routing state so as to avoid trafficloops and so forth.)

Because multiple overlay groups may, in general, hash to the same nativemulticast group, there is a potential for address collision. However,these sorts of collisions merely result in bandwidth inefficiency and donot cause packets to be incorrectly routed. The reason for this is thatthe forwarding logic in an overlay router is based on the overlayaddress carried in the overlay header, not on the native, network-layeraddress. Thus, the next-hop native multicast address need not be unique.The only adverse affect of a collision is that traffic may flow to anoverlay router that has no interest in receiving that traffic thuswasting network bandwidth. In effect, we have a tension between the sizeof the address block used (and hence the amount of group-state stored inthe native multicast routers) and the bandwidth-efficiency of thescheme.

2.2.4 Unicast-Bank VIFs

To support clients without direct multicast connectivity (which may bethe predominant form of interaction with an overlay network into theindefinite future), the overlay multicast service interface includes amechanism whereby clients can communicate directly with an overlayrouter over UDP unicast. Here; an end-host contacts the overlay routerthrough some application-specific fashion (e.g., a Web request for avideo stream) and establishes group membership for a particular overlaygroup. The setup state, including the overlay group in question, isspecified in the connection setup process, e.g., the overlay group couldbe embedded in a Web URL and HTTP could be used within an overlay routerto accept requests from senders and receivers to attach to the overlaynetwork.

Because of the transparency of the OMN infrastructure, end clients wouldnot normally know how and when to connect to an overlay router. Thus,redirection can be used (as in HTTP) to redirect a given client awayfrom the origin server that advertises streaming content, say, to anearby overlay router. A content-aware redirection server can be used tomap an IP address, for instance, to a nearby overlay router.Alternatively, in a reverse-proxy streaming configuration, the endclient could be redirected to one of a large number of overlay routersat a centralized broadcast site arranged in a cluster for loadbalancing.

There are two types of unicast-bank VIFs (UVIF): unidirectional andbi-directional. In the unidirectional variant, clients cannot sendtraffic into the OMN (though they can send application-specific feedbackto the incident overlay router), whereas in the bi-directional variant,clients can in fact do so. The former case is well matched toone-to-many applications like broadcast streaming media, while thelatter case is appropriate for many-to-many applications like videoconferencing.

As a practical concern, the unidirectional case scales more gracefullythan the bi-directional case because the packet replication process canoccur after the management and routing decision. That is, aunidirectional UVIF can simply “machine gun” a copy of a given packet toall the end-clients subscribed to the given group, rather than scheduleand process each such packet individually (thus necessitating copyingand allocating memory for this function). The bi-directional case, onthe other hand, provides richer control because it allows for fullymeshed intercommunication in a bandwidth-managed fashion.

Group membership is implied by the presence of the unicast end client.When the client requests attachment to a given overlay group, theincident overlay router treats the client as in the LVIF case andpropagates group membership state as needed to initiate reception oftraffic sent to the overlay group in question. The group membershipstate is timed out using various heuristics and application-level hints.For example, if the overlay router begins to receive port unreachable orhost unreachable ICMP messages, then the flow will be terminated and theoverlay group unsubscribed to (unless there are other hosts receivingsaid group's traffic through the UVIF). Alternatively, if the clientuses TCP control connection to initiate the UDP flow—as does theReal-time Streaming Protocol (see, RFC2326), then the presence of thepersistent TCP connection can be used to wire down the group state. Oncethe connection is closed or aborts, the state can be expired and thegroup relinquished.

3. Application Shims

Unlike the IP Multicast service model—where senders do nothing more thantransmits packets to a group address—the OMN forwarding infrastructurerequires that a source announce its presence on a well-known,domain-wide control group (i.e., via DGMP) or signaled directly to anoverlay router via SSP. If the end-hosts were OMN-aware, these controlmessages could be generated directly by the host. However, to maintaincompatibility with existing applications and reduce the burden onapplication developers, the OMN architecture assumes that some otheragent in the network can generate these messages on behalf of thesending application. An agent that provides this type of middleware glueis referred to as a “shim”.

Applications like the Real Networks G2 Server, Microsoft Netshow, CiscoIP/TV, and the MBone tools can bridge into an overlay network bybuilding shims around the applications. The shims configure the toolsappropriately and signal overlay group setup information to a nearbyoverlay router using the techniques described above. A shim can be anon-trivial application and export a sophisticated user interface. Forexample, a broadcast control center could be built that provides the OMNsignaling information to bridge between a bank of RealNetworks G2servers and a cluster of overlay routers arranged in a mesh.

Note that there is no pressing need for a specialized shim on thereceive side of an application. For example, if a receiver joins througha UVIF, the overlay router is directly informed of all required controlinformation. Likewise, if an unmodified receiver application joins amulticast group, an agent on the attached LAN can snoop the IGMP trafficand relay appropriate DGMP signaling information to the designatedoverlay router in a generic fashion. That is, the receiver need onlyspecify its presence and interest for a group and need not provide anyadditional signaling state. Shims are not necessary in all applicationsbut can be used to perform a web redirection process, as desired.

4. The Plugin Framework

Because overlay routers are situated at points of administrativedisconnect and bandwidth heterogeneity and because they areapplication-aware, they provide a strategic vantage point for carryingout traffic management that accounts for locally and globally definedadministrative policies as well as the semantics of the underlying dataflow. Traffic management in multicast is especially difficult becausethe receivers for a given group may be situated along a heterogeneousset of network paths thus preventing a source from simply sending apacket flow to all receivers at the same rate. To solve this problem,the OMN architecture includes a traffic shaping stage that is applied toeach overlay group's packet stream before it is transmitted over avirtual link in the overlay network. To effect this functionality, ahierarchical class-based bandwidth allocation scheme apportions theavailable bandwidth across a set of application-level processing agents,called plugins, that manage each group's packets.

The plugin framework transforms an overlay router into a-flexible andextensible platform for migrating application-level functionality intothe network in a safe and restricted fashion. Each media flow is boundto an application-level handler, called a plugin, that can flexiblytransform, thin, or otherwise control the flow it manages. The plugindata path is tightly integrated with forwarding semantics of theapplication data and adheres to the policy constraints imposed byexternal management and configuration tools. In a nutshell, plugins areapplication-level entities that are situated in the forwarding path ofthe overlay routers. Feedback from the packet scheduler informs theplugin of congestion and/or bandwidth availability, thereby allowing theplugin to best utilize available network resources in a tightlycontrolled fashion.

For example, a plugin might perform stream thinning within the networkaccording to the bandwidth throughput it attains from the bandwidthallocator. If a media flow is represented as a number of simulcastedsub-components, each at a different bit-rate and corresponding quality,then the plugin could forward the maximum number of streams that thebandwidth policy permits, thereby accommodating bandwidth heterogeneityfrom within the network infrastructure.

To maximize the efficacy of the application-level adaptation capabilityafforded by the plugin framework, the scheduler that controls thetransmission of packets across VIFs explicitly communicates with theplugin to adjust its rate. By providing' specific feedback as to whatrate the plugin can expect to achieve on each output link, the plugincan adjust the rate of the flow it manages to fit into its allotment.

The plugin framework is extensible. As new applications are introducedinto the network, the overlay broadcast infrastructure can be easily andincrementally upgraded by dynamically downloading plugins that handlethe new traffic types as needed. Abstractly, plugins execute in a“sandboxed” process context and intercommunicate with the overlay routerthrough a narrow application-programming interface called the PluginAPI. We can think of the overlay router plugin abstraction as an analogto Web browser plugins. Just as a browser plugin is selected based on aWeb object's Multi-Purpose Internet Mail Extensions (“MIME”—see RFCs1521 and 1522) type, the overlay router plugin is selected according tothe traffic flow type signaled via MINT.

Given the goals of this plugin bandwidth management framework, a numberof problems must be solved. First, packets must be classified, that isassigned to a certain traffic category, so that traffic can be managedin a policy-oriented fashion. Second, bandwidth must be allocated andshared among application specific processing agents. Third, packets mustbe actively scheduled to ensure that the traffic class policies andbandwidth allocations are adhered to. Finally, bandwidth policies mustbe defined, administered, and attached to the virtual links in thenetwork.

5. Routing

A collection of overlay routers forms a logical, overlay network thatprovides the conduit for efficiently distributing media flows using themulticast forwarding techniques described herein. However, in order toproperly forward packets across the overlay network, the overlay routersmust know how to route packets across the network such that allinterested receivers receive a single copy of each packet and no trafficloops arise. To this end, the OMN architecture must carry out twofundamental routing tasks:

-   -   the overlay network must compute efficient spanning-tree routes        for multicasting packets from every potential source to every        potential receiver, and    -   the network must track group membership along the distribution        tree to prevent multicast traffic from flowing where it        otherwise is not needed.

Rather than invent new routing protocols from scratch, the OMNarchitecture leverages existing multicast routing technologies thatcompute spanning trees and track group membership in a scalable fashion,but at the application layer rather than the network layer. The coreapproach is based on the Border Gateway Multicast Protocol (BGMP), butwe simplify the so-called “rendezvous problem” (see below) by explicitlyincluding the rendezvous point in the upper 32 bits of the overlay groupaddress. To scale the routing infrastructure, overlay routers may beclustered into routing “broadcast hubs”, where the routers that comprisethe hub are interconnected with a high-speed multicast-capable LAN.Hubs, in turn, are interconnected across the wide area. In this way,traffic can be load-balanced between wide area hubs by spreading groups(i.e., broadcast channels) across multiple overlay routers. Likewise,unicast join requests can be distributed evenly across a broadcast hubto balance the load of an arbitrary number of client viewers.

7.1 Multicast Routing Background

The fundamental problem in multicast routing is to build up state in thenetwork that interconnects each source with every interested receivervia some sort of routing tree. This is typically called the “rendezvousproblem”, i.e., how multicast' receivers and sources find each other ina scalable distributed fashion. Roughly speaking, there are twofundamental approaches to this problem: (1) broadcast traffic everywhereand prune it back from regions of the network where there are nointerested receivers, and (2) broadcast traffic toward a core and havereceivers join a broadcast channel by sending control messages to thatcore.

Unfortunately, “broadcast and prune” is quite unscalable since trafficgoes everywhere in the network. On the other hand, anchoring a tree at acore (or “rendezvous point”) in the network is more scalable but has thedisadvantage that the participants must know where the core is (or thenetwork must maintain a mapping from multicast group addresses tocores). A number of ad hoc approaches for this have been proposed in theresearch literature (for CBT and SM-PIM), but BGMP takes a novelapproach where multicast addresses are bound to source domains. In thismodel, the network maintains a distributed mapping between multicastaddresses and source domains. A key novelty in BGMP is to represent thismapping as a set of routes. That is, each BGMP domain is configured withone or more blocks of multicast addresses and that BGMP domainadvertises these blocks (via scalable prefixes) across the BRs using arouting protocol like M-BGP, a Border Gateway Protocol for exchangingrouting information between gateway hosts. The effect is that eachborder router then knows the shortest path toward the “owner domain” ofa given block of multicast addresses. Thus, when a border routerreceives a join message for a given group, it can consult this auxiliaryrouting table to propagate the join toward the source domain and recordor modify the “local view” of the multicast spanning tree in aforwarding table (the Forwarding Information Base or FIB). In short, theM-BGP routing table is used exclusively to set up the bi-directionaltree and once the tree state is established in the FIB, the borderrouter consults only the FIB to make forwarding decisions. In BGMPterminology, the source domain is called the “root”, the routing tableof multicast address blocks is called the “multicast RIB”, and theforwarding table constructed from join/leave BGMP messages (which arerouted via the RIB) is called the “tree state table”.

Given that this scheme relies upon each root domain owning some set ofmulticast address blocks, the natural question arises as to how theseaddresses are allocated in a decentralized, robust fashion. To this end,BGMP proposes that some companion protocol issue address blocksdynamically across domains in a hierarchical fashion. The MulticastAddress Set Claim (MASC) protocol has been proposed to serve thisfunction for BGMP. The basic model in MASC is to arrange domains into ahierarchy and have children domains request blocks of multicastaddresses from their parents, which in turn requests larger blocks fromtheir parents, and so on up to some top-level domain that owns theentire multicast address space. The address blocks are claimed andreleased using timeouts in a fashion similar to how Dynamic HostConfiguration Protocol (DHCP—RFC2131) allocates temporary IP addressesin a local network.

Unfortunately, the dynamic approach to address allocation taken by MASCintroduces substantial complexity and potentially hard-to-predictdynamics. It is also not clear how top-level addresses will be arrangedor what incentives will be in place to prevent sub-domains fromrequesting too many addresses. Moreover, the architecture relies uponaddress allocation preemption, where if a parent domain reclaims a blockof addresses, all the applications that are using that address mustperform reallocation, presumably in some synchronized fashion. Inaddition, this framework is complicated by the fact that address blockswill become fragmented over time as applications allocate and releaseaddresses from the various available blocks. In short, maintaining adecentralized, robust address allocation architecture, especially in theface of intermittent connectivity that is so commonplace in theInternet, appears to be fragile and difficult to deploy. Fortunately,these problems can be quite easily overcome if the address architecturecan be changed (and since we are building a new overlay networkinfrastructure, this is easily done). By using a 64-bit address for thebroadcast channel address, the IP address of the. core can appearexplicitly as the upper 32-bits of the overlay address.

The beauty of embedding prefix-based root domains in a larger address isthat the resulting scheme is completely compatible with the BGMPmulticast RIB because the root domain prefix is simply treated asadditional bits of the multicast address. And the M-BGP styleaggregation of multicast address blocks only requires a routecomputation that effectively uses root domain identifiers instead ofmulticast address blocks (because they are one in the same). In short,the RIB is a routing table that gives shortest path routes to therendezvous points and has no dependence per se on overlay groupaddresses.

In light of this discussion, the OMN architectural components foroverlay multicast routing are based on:

-   -   a path-state routing (PSR) protocol to compute shortest-path        routes toward the rendezvous point, and    -   an overlay group membership (OGMP) protocol based on BGMP to        track group membership across the OMN.

7.2 Path-State Routing Protocol (PSR)

In order to effectively build the multicast spanning trees, each overlaynode must know the next hop along the shortest path from that node tothe rendezvous point. That is, spanning trees are incrementally built upas group membership requests (graft and prune messages) are sent towardthe rendezvous point according to the group's route. Thus, overlayrouters run a distributed routing algorithm to compute these shortestpaths.

As in BGMP, the OMN architecture exploits a path-state routing protocolto compute such routes. Any node in the overlay network may beconfigured as the rendezvous point for some set of overlay addressprefixes (i.e., which may be the unicast address prefixes of theparticular set of hosts within its domain). Once so configured, a nodeadvertises “reachability” to that rendezvous point via itself. In turn,its directly attached neighbors propagate this reachability informationto its neighbors and so forth. As in BGP, each advertisement includesthe entire path of nodes to which the route corresponds, which allowsthe system to easily detect and avoid potential routing loops, andallows administrative policies to control how routes are filtered andpropagated. As described above, the OMN architecture accounts for andoptimizes the case that transit domains are implemented using nativemulticast. That is, overlay routers forward packets to a group of peerrouters simply by transmitting a single copy using native multicast.This, however, has no bearing on the path-state routing computationsince this method of forwarding is isomorphic with that of unicasting acopy to each peer. And, in the overlay topology, each peeringrelationship across a multicast transit VIF is managed as if it were aseparate, point-to-point connection.

7.3 Group Membership

When a host joins (or leaves) an overlay group at the edge of thenetwork, group membership state must be reflected into the network in ascalable fashion. The Overlay Group Management Protocol (OGMP) carriesout this function by tracking group membership requests at an overlaynode and propagating them as necessary to the appropriate peers based onthe PSR routing data base.

As in BGMP, the OMN architecture effects group membership through agraft/prune protocol. When a host joins a group, a join message is senttoward the rendezvous domain (which is explicitly given in the joinrequest) using PSR routes. As soon as the join messages reaches a routerthat is already on the tree, the message stops. The message is senthop-by-hop toward the rendezvous point across a TCP control connectionthat manages the peering relationship of each pair of overlay nodes. Asin BGP and BGMP, the use of TCP connections provides reliability andflow control and thereby simplifies the routing protocol.

Likewise, when a source joins a group, a join message is sent toward(and all the way to) the rendezvous point. This implies that trafficflows to the rendezvous point even if it is not necessary to do so toreach all interested receivers. A future version of the group membershipprotocols may be more sophisticated and avoid this condition.

7.4 Loop Avoidance

A standard problem in both unicast and multicast routing protocols istraffic loops that are caused by inconsistent views of the routingdatabase at different points in the network. This problem couldpotentially be exacerbated by the application-level nature of the OMNarchitecture and the interaction of the application-level routinginfrastructure with the underlying network-level multicast layer. Inthis section, we discuss this interaction and argue that the OMNarchitecture is in fact robust against looping pathologies.

One challenges posed by the OMN architecture is that the underlyingmulticast regions used to glue together distinct multicast transit VIFSmight not be completely partitioned from One another simply because suchisolation might be hard to configure (and in fact is difficult toautomatically ensure). Thus, we could end up in a situation where anoverlay router R receives a packet say from multicast TVIF V1 andforwards it to TVIF V2 (out a separate physical interface). But if forsome reason these two domains overlap physically, then the packetforwarded to V2 would reappear on domain VI and R might forward it againcreating a routing loop.

Fortunately, the application-level nature of the OMN leads to an easysolution for this problem whereby we leverage the peering relationshipthat already exists among overlay routers. As such, a router forwards apacket only if it arrives from one of its peers within the appropriatetransit VIF. That is, a router accepts a packet only if it came-from apeer router that it expected it to come from (which it can check since,unlike network-layer multicast, the peer's IP address appears explicitlyin the packet). Thus, in the case above, R would see that the secondcopy of the packet from VIF VI had originated from itself and thereforedrop it. Note that this scheme generalizes correctly to indirect loopsinvolving multiple VIFs because the set of peers incident to a multicastVIF are configured into each overlay node.

The other case of concern is when an overlay router accepts a packetfrom a multicast leaf VIF. Here, the router must be sure that the sourceof the packet is an end host and not another overlay router (that, forinstance, might be leaking packets into the leaf domain coincidentally).Since the OMN architecture requires that senders explicitly signal theirpresence using SSP, the overlay router knows whether any given packet isfrom a legitimate sender in that leaf VIF. Note that this is anotherexample where routing at the application layer provides a simplesolution to hard problems—since the routers appear explicitly in theforwarding function we can easily detect loops using simple consistencychecks.

7.5 Black Hole Avoidance

One of the major difficulties of interoperability between multicastrouting protocols is to ensure that disparate routing entities agree onthe overall multicast routing tree for any given group. That is, when apacket crosses a routing domain, it must enter the new domain at a pointthat is topologically matched to that domain's view of the distributiontree. Yet, if the outer-domain protocol has an alternate viewpoint, thepacket arrives at the wrong location and is dropped. A substantialfraction of the complexity of the BGMP protocol specification has to dowith making sure this mismatch is properly handled for the variousmulticast routing protocols that exist.

However, just as application-level routing made the loop avoidanceproblems easy, it likewise provides an easy solution for avoiding blackholes. Because network layer addresses are rewritten on each hop throughthe OMN, there is no need for overlay routers to ensure that the leafdomain multicast routes are congruent with the OMN world view. That is,when a packet is injected into a leaf or transit multicast VIF, the IPsource address corresponds to the overlay router not the originalsource. Thus, black holes cannot occur because this traffic is routedexclusively against local rules in the containing overlay scope, whichare not susceptible to any wide-area state.

A disadvantage of this approach, however, is that the original sourceaddress does not survive in tact and thus a multicast receiver has nodirect means to identify the address of the origin. Instead, the OMNmodel assumes that transport-level protocols either provide their ownmechanisms for source identification (as in RTP): or that applicationsare agnostic to the origin address (as with streaming media players fromMicrosoft and RealNetworks).

Transaction Example in the OMN Architecture

Next, a description of hardware suitable for use with the presentinvention is presented, followed by a detailed walk-through ofinformation transactions using the overlay approach of the presentinvention.

Description of Hardware

FIG. 3A is an illustration of computer system 1 including display 3having display screen 5. Cabinet 7 houses standard computer components(not shown) such as a disk drive, CDROM drive, display adapter, networkcard, random access memory (R.AM), central processing unit (CPU), andother components, subsystems and devices. User input devices such asmouse 11 having buttons 13, and keyboard 9 are shown. Other user inputdevices such as a trackball, touch-screen, digitizing tablet, etc. canbe used. In general, the computer system is illustrative of but one typeof computer system, such as a desktop computer, suitable for use withthe present invention. Computers can be configured with many differenthardware components and can be made in many dimensions and styles (e.g.,laptop, palmtop, pentop, server, workstation, mainframe). Any hardwareplatform suitable for performing the processing described herein issuitable for use with the present invention.

FIG. 3B illustrates subsystems that might typically be found in acomputer such as computer 100.

In FIG. 3B, subsystems within box 20 are directly interfaced to internalbus 22. Such subsystems typically are contained within the computersystem such as within cabinet 7 of FIG. 3. Subsystems includeinput/output (I/O) controller 24, System Random Access Memory (RAM) 26,Central Processing Unit (CPU) 28, Display Adapter 30, Serial Port 40,Fixed Disk 42 and Network Interface Adapter 44. The use of bus 22 allowseach of the subsystems to transfer data among the subsystems and, mostimportantly, with the CPU. External devices can communicate with the CPUor other subsystems via bus 22 by interfacing with a subsystem on thebus. Monitor 46 connects to the bus through Display Adapter 30. Arelative pointing device (RPD) such as a mouse connects through SerialPort 40. Some devices such as Keyboard 50 can communicate with the CPUby direct means without using the main data bus as, for example, via aninterrupt controller and associated registers (not shown).

As with the external physical configuration shown in FIG. 3A, manysubsystem configurations are possible. FIG. 3B is illustrative of butone suitable configuration. Subsystems, components or devices other thanthose shown in FIG. 3B can be added. A suitable computer system can beachieved without using all of the subsystems shown in FIG. 3B. Forexample, a standalone computer need not be coupled to a network soNetwork Interface 44 would not be required. Other subsystems such as aCDROM drive, graphics accelerator, etc. can be included in theconfiguration without affecting the performance of the system of thepresent invention.

FIG. 3C is a generalized diagram of a typical network.

In FIG. 3C, network system 160 includes several local networks coupledto the Internet. Although specific network protocols, physical layers,topologies, and other network properties are presented herein, thepresent invention is suitable for use with any network.

In FIG. 3C, computer USER1 is connected to Server 1. This connection can15 be by a network such as Ethernet, Asynchronous Transfer Mode, IEEEstandard 1553 bus, modem connection, Universal Serial Bus, etc. Thecommunication link need not be a wire but can be infrared, radio wavetransmission, etc. Server1 is coupled to the Internet. The Internet isshown symbolically as a collection of server routers 162. Note that theuse of the Internet for distribution or communication of information isnot strictly necessary to practice the present invention but is merelyused to illustrate a preferred embodiment, below. Further, the use ofserver computers and the designation of server and client machines isnot crucial to an implementation of the present invention. USER1Computer can be connected directly to the Internet. Server1's connectionto the Internet is typically by a relatively high bandwidth transmissionmedium such as a T1 or T3 line.

Similarly, other computers at 164 are shown utilizing a local network ata different location from USER1 computer. The computers at 164 arecoupled to the Internet via Server2. USER3 and Server3 represent yet athird installation.

Note that the concepts of “client” and “server,” as used in thisapplication and the industry, are very loosely defined and, in fact, arenot fixed with respect to machines or software processes executing onthe machines. Typically, a server is a machine or process that isproviding information to another machine or process, i.e., the “client,”that requests the information. In this respect, a computer or processcan be acting as a client at one point in time (because it is requestinginformation) and can be acting as a server at another point in time(because it is providing information). Some computers are consistentlyreferred to as “servers” because they usually act as a repository for alarge amount of information that is often requested. For example, aWorld Wide Web (WWW, or simply, “Web”) site is often hosted by a servercomputer with a large storage capacity, high-speed processor andInternet link having the ability to handle many high-bandwidthcommunication lines. A server machine will most likely not be manuallyoperated by a human user on a continual basis, but, instead, hassoftware for constantly, and automatically, responding to informationrequests. On the other hand, some machines, such as desktop computers,are typically thought of as client machines because they are primarilyused to obtain information from the Internet for a user operating themachine.

Depending on the specific software executing at any point in time onthese machines, the machine may actually be performing the role of aclient or server, as the need may be. For example, a user's desktopcomputer can provide information to another desktop computer. Or aserver may directly communicate with another server computer. Sometimesthis is characterized as “peer-to-peer,” communication. Althoughprocesses of the present invention, and the hardware executing theprocesses, may be characterized by language common to a discussion ofthe Internet (e.g., “client,” “server,” “peer”) it should be apparentthat software of the present invention can execute on any type ofsuitable hardware including networks other than the Internet. Althoughsoftware of the present invention, such as the MediaBridge software, maybe presented as a single entity, such software is readily able to beexecuted on multiple machines. That is, there may be multiple instancesof a given software program, a single program may be executing on two ormore processors in a distributed processing environment, parts of asingle program may be executing on different physical machines, etc.Further, two different programs, such as a client and server program,can be executing in a single machine, or in different machines. A singleprogram can be operating as a client for one information transaction andas a server for a different information transaction.

FIGS. 4A-C are next discussed to present two examples of initiating andmaintaining an overlay multicast from a content source to a requestingdestination computer. The two examples differ only in the manner inwhich the destination computer makes a request to be included as arecipient of the multicast content information. In the first example,the overlay multicast is initiated by a unicast request from thedestination computer. In the second example the overlay multicast isinitiated by a native multicast request from the destination computer.

In the Figures, an “M” in a box indicates a MediaBridge computer thathandles the overlay routing of the invention as discussed above. An “R”in a box indicates a router, such as a typical router on an intranet,the Internet, or other network where the router manages the flow ofinformation to, and from, a local, or otherwise defined relativelyself-contained, network that is connected to other networks which arealso managed by associated routers. In the Figures, one router isassumed to manage a single local area network (LAN) and one MediaBridgecomputer is assigned to each network that can receive overlay multicastinformation, or that can act as a router for overlay multicastinformation, according to the present invention. MediaBridge computersare not strictly required on every LAN. Unicast attachment with thenetwork allows a MediaBridge to be situated arbitrarily far from theclient but, in general, the closer proximity of MediaBridges to clientsaids in overlay routing. As discussed above, MediaBridge computers forman overlay network where the computers are in a peering relationshipwith each other. MediaBridge computers maintain tables of overlay groupswhich are updated via a membership protocol. The tables are used toroute information between the MediaBridge computers according tosubscriptions, or memberships, to the overlay groups. Critical to therouting is a mapping of overlay groups to native groups by using thetables.

FIGS. 4A-C show more detail than in FIG. 2 by depicting individualend-user, or “host,” computers, routers and MediaBridge computers; butotherwise show the same architecture as in FIG. 2. For example, group ofnetworks 120 is a “transit domain” as depicted in FIG. 2 while the otherLANs can be considered “leaf domains” as discussed above. Across transitdomains native multicasting is preferably used to achieve overlayforwarding through unicast, peer-to-peer or other types of prior artrouting can be used to achieve the overlay routing. Note that thespecific topology, interconnections and number and type of devices shownin the Figures is only for purposes of illustrating the followingexamples, it should be readily apparent that many arrangements ofcomputers, routers, wide or local area networks, physical links, orother processing devices or communication structures may be used withthe invention.

FIG. 4A shows a unicast-initiated overlay routing aspect of the presentinvention.

In FIG. 4A, the goal is to have streaming media information, such asvideo program digital data including image and audio information,originate from source computer 100 to be received by destinationcomputer 102. Naturally, many other destinations will exist in a typicalmulticast of information. The same mechanisms and techniques discussedhere with respect to the single destination 102 can apply to any numberof destinations. Because of the use of an overlay address and mappingprotocol, the system of the present invention scales easily withoutrequiring changes to existing network software and hardware.

Although the invention is discussed with respect to multicasting ofstreaming media information, any type of information can be distributedover a network by using the techniques of the present invention. Forexample, Internet distribution of software applications and updates,stock quotes, web pages, web cache updates, news, etc., can all bedistributed more quickly, more efficiently, and with more control andmonitoring by using the techniques of the present invention.

The present invention allows each potential recipient of a multicast toexplicitly request the information. Such a request can be performed bythe selection of a human user at the requesting computer, can beinitiated automatically by a computer, or can be achieved by othermeans.

FIG. 4A shows the case where the receipt of multicast information isinitiated by a unicast manner in response to a user's request.Specifically, destination 102 is a desktop computer operated by a userwho is browsing web pages. In general, any type of computer running anynumber of applications, operating ‘systems, user environment, etc., issuitable for use with the present invention. The web page that the useris currently viewing on the desktop computer is “served” by web servercomputer 104. Web server 104 stores, and serves, information to othercomputers, such as destination computer 102, in the form of web pagecontent, hyperlinks (i.e., uniform resource locators or “URLs”) andother formats.

In the present example, the link of interest is a link to receive thestreaming media video production which is to be provided by sourcecomputer 100. The data from source computer 100 may already be streamingwhen destination computer 102 makes a request for the stream.Preferably, source computer 100 registers its channel with the overlaynetwork so that other MediaBridges and web servers “know” how toassociate an overlay channel with the data stream. For example, adirectory services table can be maintained by web server 104 so that webserver 104 can carry out the redirection process for a publishedchannel. When the user of destination computer 102 chooses to receivethe video program, e.g., by clicking on a link, web page graphic, symbolor other control, web server 104 transfers information on how tosubscribe to the video program as shown by the path 106. In thepreferred embodiment, the transactions between destination computer 102and web server 104 are governed by HTTP/TCP. However, it should beapparent that the invention is adaptable to a variety of differentnetwork communication protocols and standards.

Web server 104 returns the identification for MediaBridge computer 108(referenced as M_(I) in FIG. 4A) to destination computer 102. Web server104 makes the decision to have destination computer 102 route throughMediaBridge computer 108 since web server 104 is provided withinformation associating computers on the Internet with optimalMediaBridge computers. In the preferred embodiment, the optimalMediaBridge computer that a destination computer will use is generallythe MediaBridge computer closest in proximity to the destinationcomputer. Proximity can be a factor of both geographic distance and theelectronic network path between the destination and MediaBridgecomputers.

In the present example, web server 104 is provided with information onmaking the association between a destination computer and a MediaBridgecomputer as, for example, where a table in web server 104 associates oneor more destination computers with a specific MediaBridge computer. Notethat it is possible to have such associations performed by anothercomputer rather than the web server. For example, a MediaBridge, orother computer, connected on a local area network to web server 104 canbe used. Also, the computer making the destination computer andMediaBridge computer association can be remote from web server 104,although the web server requires access to the mapping table to redirectdestination computer 102 correctly.

In a first approach to connecting destination computer 102 to the mediastream, web server computer 104 can provides an overlay channelidentifier to destination computer 102. The channel identifier is usedby the various MediaBridge computers to route the proper content to adestination computer. The channel identifier, or channel address, is 64bits in the preferred embodiment. A channel name is used in the LTRL andis mapped to a corresponding channel ID as part of the redirectionprocess. Optionally, other information can be provided by the webserver. Such additional information can be used either by destinationcomputer 102 to make the subscription request, or can be used by aMediaBridge computer to service subscription requests and to provideefficient multicast relaying. For example, statistics can be kept aboutthe requesting user's computer, geographic location, etc. This can beused for demographic analysis, to make predictions about the destinationcomputer's ability to process data at a sufficient bandwidth, or forother reasons.

Once destination computer 102 has been provided with the appropriateMediaBridge computer address and channel identification information thedestination computer makes a subscription request to MediaBridgecomputer 108.

FIG. 4B illustrates a next major step in the setup for overlay routingin the present example.

In FIG. 4B, once destination computer 102 acquires the subscriptioninformation from web host 104, destination computer uses thesubscription information to send out one or more packets that indicatethat MediaBridge computer 108 is to receive the subscribed channel. Inthe preferred embodiment, the subscription data includes anidentification of the desired channel, i.e., the video program, that isto be received, the destination computer's identification (namely,destination computer 102), and other information. Note that the locationof the MediaBridge computer can be different from that shown in FIG. 4B.Specifically, the MediaBridge computer can exist anywhere on theInternet and need not be part of the LAN that the destination computeris on.

Once MediaBridge 108 receives destination computer 102's subscriptioninformation, MediaBridge computer 108 uses the overlay channel ID toinitiate the subscription process. The subscription process is acombination of the native multicasting network architecture and theoverlay multicast architecture as described in detail, above.Ultimately, MediaBridge computer 108 sends one or more packets ofinformation in an attempt to subscribe to the appropriate nativemulticast group. For purposes of the example, we assume that theappropriate native multicast group to which MediaBridge M2 willsubscribe for purposes of handling the overlay routing with region 120needed by the video program from source 100 to destination 102 isdesignated as “a.” The overlay multicast group that is associated withthe native multicast is designated as “A.”

In the preferred embodiment, a direct 1-to-1 mapping of native tooverlay groups is not possible since a native group uses 32 bits for anaddress and an overlay address is 64 bits. The upper-32 bits are used tospecify a rendezvous point. A rendezvous point lookup algorithm can belocally configured, for example, into an agent that monitors IGMPmessages. Another possibility is to have the rendezvous point selectionalgorithm provided in a fashion similar to the unicast case where theoverlay group address is stored at a MediaBridge by a redirectionprocess (discussed below) and where the client is instructed to nativelyjoin group “a.”

A second approach to unicast-initiated overlay routing provides achannel name used in the original requesting URL to be mapped to acorresponding overlay group as part of the redirection process. When theclient attempts to retrieve the resource identified by this URL, theserver generates a response that redirects the client to MediaBridge108. The client may or may not be explicitly aware of the protocols inuse to effect overlay multicasting. If the client is overlay-multicastcapable, the overlay group can be included in the response message andthe client can connect to MediaBridge 108 using overlay-multicastspecific protocols. If, however, the client is not capable ofparticipating in the overlay multicast protocols (e.g., because theclient is an existing piece of software that has a large installedbase), then the client can communicate with MediaBridge 108 using itsexisting, unmodified control protocol (e.g., Real-Time StreamingProtocol (RTSP) as specified in Internet-draft for RTSP, Mar. 27, 1997).Since the overlay group may not be transportable through that existingprotocol, yet is required by MediaBridge 108 to join the broadcastchannel, the server (104) contacts MediaBridge 108 with the overlaychannel to use before generating the response to the original Webrequest from the client (102). As part of the dialogue, the MediaBridgereturns a “port” identifier to the server (104), upon which it thenawaits the client-specific connection. This allows the server (104) torespond to the client with a message that redirects the client to thesubsequent port, thereby ensuring that the requesting client is properlyassociated with the overlay group temporarily stored at MediaBridge 108.

FIG. 5 illustrates the second approach to unicast-initiated overlayrouting.

In FIG. 5, which corresponds to FIGS. 4A-C, destination computer 102makes request 160 to web server 104 via, for example, clicking on ahyperlink to obtain the media stream. Web server 104 deposits state atMediaBridge computer M1 representing the overlay group channel “A” and astreaming media URL, e.g.,“rtsp://serverfastforward.com/live/olympics.rm”, as shown by path 162.Next, M1 returns to web server 104 an identification that TCP port “p”is the port on which requesting computer 102 should connect as shown bypath 164. Web server 104 responds to requesting computer 102 with amessage that redirects requesting computer 102 to stream media from M1over port “p” as shown by path 166. Requesting computer 102 initiates astreaming media protocol, such as RTSP, by contacting M1 over port “p”as shown by path 168. M1 sends a subscription request for group “A” toM2 as shown by path 170. Packets, or portions, of information sent fromthe content source will then be relayed via the overlay routing to M1and to requesting computer 102.

The request to subscribe is transferred through router R_(I) to otherrouters on the Internet. The subscription request installs a forwardingstate in the MediaBridges that indicates which peer MediaBridges arepart of the spanning tree for the given overlay channel. An example of a“domain,” or “region,” of routers and MediaBridge computers is shown at120 in FIG. 4B. A region is simply a portion of the Internet, or othernetwork, that is logically, geographically or, due to network trafficconsiderations, that provides efficiencies in multicast distributionwhen two or more MediaBridge computers implement an overlay networkwithin the region. Within a given region, there is a mapping of eachoverlay channel to a single native multicast channel. In the preferredembodiment this occurs via a “hash” function, as described above.However, as information is propagated among regions there will typicallybe different native multicasting channels used for a given portion ofinformation, or packet. For various reasons, the native and/or theoverlay channel mappings for a particular multicast stream can change.For example overloading or failures can cause rerouting and remapping ofchannels.

Ultimately, the MediaBridge computer 108 sends one or more packets ofinformation in an attempt to subscribe to the overlay group in question.The next few paragraphs describe an example of subscribing to an overlaygroup. The protocol for performing the subscription is called theoverlay group membership protocol (OGMP). For the example, the overlaygroup is designated “A”; likewise, the symbol “a” denotes the nativegroup that is computed from “A” using the overlay scope defined byregion 120.

A subscription message is sent from MediaBridge 108 to the peer on theshortest path route, as determined by a path-state routing computation,to the rendezvous point for “A”. In this example, we assume therendezvous point is MediaBridge M6 (it may be any MediaBridge in theoverlay network, but it is most efficient to choose the rendezvous pointnear the broadcast source). Recall that the upper 32-bits of the overlaygroup represent the IP address of the rendezvous point.

In the configuration show in FIG. 4B, the peer on the shortest path fromMediaBridge 108 to the rendezvous point (M6) is the MediaBridge labeledM2. Thus, MediaBridge 108 sends a “subscription request” for the overlaygroup in question to MediaBridge M2. In turn M2 propagates thesubscription message to its peer that lies upon the shortest-path routeto the rendezvous point, which in this case is MediaBridge M4. Likewise,M4 sends the request to M6. (These messages are sent reliably usingTCP.) Each time a subscription message is received and processed by aMediaBridge, the MediaBridge records subscription information for thegroup in question and updates its forwarding information base so thatwhen packets are received they can be properly routed to the peerssubscribed to said overlay group.

In the case of a multicast transit VIF, the MediaBridge mustadditionally decide which native group to join using the prior artprotocols as a function of the overlay group. For example, when M2receives the subscription request, it joins the native multicast group“a” in addition to forwarding the subscription request for “A” onto M4.Thus, when M4 receive data packets addressed to overlay group “A”, itwill forward them into the overlay scope defined by region 120 bytransmitting the overlay packet addressed to native group “a”. Since M2is has joined native group “a” using prior art protocols, it willreceive said packet and in turn can forward that packet to itsdownstream peer M1.

After MediaBridge M_(I) 108 has subscribed to the appropriate nativemulticast group, “a” in this example, it will receive native multicasttransmissions for the group. Once MediaBridge computer 108 has joinedthe native multicast channel, it begins to receive information for thevideo program. This is illustrated in FIG. 4C by path 122. Although aspecific routing is illustrated in FIG. 4C, naturally any number, andconfiguration, of routers, switches, servers or other devices can beused. Furthermore, the physical channel can be hardwire; radio-frequencysignals, infra red signals, fiber optic light-signals, etc.

Once the overlay group, and group routing tables, information isdistributed and stored, data transfer from source computer 100 canproceed accurately. Data is forwarded from source computer 100 toMediaBridge computer M₆ receives packets from source computer 100 andadds a header with the overlay group address to each packet. Each packetis then forwarded to M₄. M₄ multicasts the packets to the native group“a.” M₂ receives the packets as M₂ is listening to native group “a” as aresult of the association of “a” with “A” in the tables. M₂ forwards thepackets to M_(I). M_(I) strips off the overlay header and forwards thenative packet to the client, destination computer 102.

Naturally, any other computers on LAN 126 are also provided with thesame packets if they have subscribed to overlay channel “A.” Thus, thisapproach of overlaying a multicast channel designation onto an existingnative multicast channel designation is able to benefit from nativemulticast according to the prior art. In addition, the act of using anoverlay channel designation allows MediaBridge computers to regulate,and otherwise control, the transmission of packets associated with aspecific stream to computers on the same local network as theMediaBridge computer. Another advantage is that, where additionaldestination computers such as 124 are “downstream” from transit domain120 and also desire to receive on overlay channel “A,” duplication ofpackets to the transit domain, and over links within the transit domain,is not necessary. Thus, the broadcast scales efficiently because onlyone copy of each packet needs to be sent to the transit domain from thecontent source via MediaBridge M6, and only one copy of each packet istransferred between MediaBridges within the transit domain.

Although the present example discusses a single MediaBridge computerassociated with each local area network, other arrangements arepossible. For example, a MediaBridge computer can be associated withmore than one local area network where the networks are connected.Additionally, there may be more than one MediaBridge computer for asingle local area network to provide fault tolerance and stability. Theselection of the number of MediaBridge computers to use for a givennumber of networked computers, subnetworks, regions, domains, etc., ismade based on the overall topology of the network area involved, trafficconsiderations, control requirements, etc. In general, there can bemultiple transit domains interconnected in arbitrary ways byMediaBridges, or processors or processes performing one or more of theMediaBridge functions discussed herein.

As each MediaBridge computer receives information, or packets,designated for an overlay channel that the MediaBridge is participatingin as a relay device, the MediaBridge computer checks aninternally-stored table (i.e., the FIB) for the Internet protocol (IP)address of each peer machine that should receive the packet to ensurethat the packet arrived from an acceptable peer. If so, the tableindicates the IP addresses of additional peers to which the packetshould be forwarded. It then transfers, or relays, copies of the packetto each of these machines. The preferred embodiment transfers thepackets by using standard User Datagram Protocol (UDP). The efficiencyof this distribution with respect to the present invention is largelydetermined by how a network administrator sets up the location ofMediaBridges and the peer-to-peer tables in each MediaBridge computer.Naturally, one desirable scheme would minimize the amount of repetitiousrelays of the same packets to different MediaBridges by configuring thetables of peering relationships in a geographic, logical or networktraffic sense, or in another arrangement designed to improve throughput,efficiency, control, monitoring or some other desirable goal. Efficiencyof the overlay multicast system also depends on the extent to whichnative multicasting can be used to effect transfers.

Note that, that any point where a MediaBridge computer is in a store-andforward position with respect to the streaming content that theMediaBridge computer can make decisions as to whether, and where, toroute the packets. In other words, every time a MediaBridge computer isused to relay a packet, there can be a control mechanism forrestricting, managing or modifying the relayed information. Aspects ofthe present invention relating to management and control of the mediastream are discussed in detail in the co-pending patent application(s)referenced at the beginning of this specification.

Assume that the video program is a television program with commercialslots. MediaBridge computer M₂ can be used to insert a locallycustomized commercial into an appropriate commercial slot. MediaBridgecomputer M1 can be used to restrict the video program entirely (e.g., apay-per-view presentation) from some computers and allow it to others inLAN 126. Or, where MediaBridge computer 108 determines that thebandwidth requirements of streaming the complete video program are toohigh for LAN 126, MediaBridge computer 108 can restrict the bandwidth ofthe video program, e.g., by reducing the image size, resolution, framerate, color depth, etc. Other benefits are possible. For example, anyMediaBridge can store, or cache all, or a portion of, the video programinformation. Caching decisions can be controlled by administrativelyspecified bandwidth policies and traffic classes as described inco-pending patent application(s) referenced at the beginning of thisspecification.

In the discussion above, FIGS. 4A-C have illustrated a unicast-initiatedoverlay routing scenario. Another type of scenario is initiated in amulticast manner and is referred to as multicast-initiated overlayrouting.

Multicast-initiated overlay routing differs from unicast-initiatedoverlay routing only in the manner that the destination computersubscribes to the content stream. In contrast to the, unicast-initiatedapproach, the multicast-initiated approach allows a destinationcomputer, such as destination computer 102 in FIGS. 4A-C, to make arequest via. a native multicast to join a particular native multicastgroup. For example, in the discussion above with respect to FIGS. 4A-C,destination computer 102 can make a multicast request to join nativemulticast group “a.” MediaBridge computer 108 is programmed to detectsuch requests by monitoring IGMP traffic on the LAN, and processes therequest by performing the steps described above to subscribe to nativemulticast group “a”.

Table I, below, provides an overview summary with respect to datastructures and how they are created and used in the examples discussedabove in FIGS. 4A-C. Note that, although specific mechanisms, formatsand uses are mentioned in relation to the data, that other possibilitiesare within the scope of the present invention. For example, tables canbe constructed, modified, transferred and maintained (i.e., “processed”)by manual means, or automatically by one or more processors orcomputers. The data and data structures can be processed by any priorart methods, systems and protocols or can be processed by specific newtechniques as presented in this specification. The steps of Table I canbe performed in a different order than the order shown in Table I. Also,all of the steps of Table I may not be necessary to practice theinvention and additional steps can be included without exceeding thebounds of the invention.

TABLE I 1. A link registry is stored in, or made available to, R7. Thelink registry associates MediaBridge MI with computers on Ml's LAN,including destination computer 102. 2. Mapping tables associating M2,M3, M4 and M5 via a native multicasting channel are determined forpurposes of native multicasting information within transit domain 120.3. A request is made by content source 100 to register with the overlaynetwork. This is handled by using an external directory source. Theassociation between the content source and the overlay channel groupdesignation can be transferred among MediaBridges. 4. Destinationcomputers, such as destination computer 102 make requests for contentinformation. Examples of how this is done include (a) using a hyperlinkto receive a URL from web server 104 that redirects destination computerto MediaBridge Ml according to the link registry at R7, where theredirection includes an identification of the content source such as byusing the content source's overlay address, “A”; (b) destinationcomputer 102 makes a unicast or multicast request of a MediaBridge, suchas Ml, for content by using the content source's native address, overlayaddress or other identification. 5. MediaBridge Ml sends a subscriberequest for the content source information by using the overlay address“A” or other identification. 6. MediaBridge M2 receives the subscriberequest and adds an association of overlay group address “A” with Ml sothat packets from content source 100 received by M2 are sent to Ml andeventually to destination computer 102. Note that subscription can occurprior to, during, or even after content source 100 begins streamingdata. 7. As M6 received packets from content source 100, M6 adds aheader corresponding to. the overlay group address “A” to each packet.Each packet with header “A” received by any of the MediaBridges is sentalong the associated paths to other MediaBridges. This means thatMediaBridges within the transit domain receive “A” packets via nativemulticast over channel “a”. To achieve native multicast, the overlayaddress is included in the overlay header and carried in the nativemulticast packet. MediaBridges can add back the overlay address in theheader for subsequent delivery to other MediaBridges. For example, M2'stransmission of “A” packets to Ml includes the overlay address in theheader. This allows Ml to continue overlay routing within M1's LAN ofmultiple overlay channels. . 8. At each receipt of packets within aMediaBridge, benefits of bandwidth management, control, monitoring andother features through additional processing are possible as discussedherein and in co-pending patent applications referenced above.

FIG. 6 illustrates details of header and address processing in thepresent invention.

In FIG. 6, content source 202 sends information in the form of packetssuch as packet 204. Packet 204 includes an IP header 206 having adestination field and source field. The destination field indicates thatthe packet is destined for MediaBridge M1 and that the source for thepacket is S. The packet data is contained in a UDP format “payload” 208.When MediaBridge computer M1 received the packet, it changes thedestination and source indications to M2 and M1, respectively.Additionally, an overlay header is inserted between the IP header andthe payload. This packet is shown at 210. The overlay channel indicationis “A” in the overlay header, which is also in UDP format.

Packet 210 is received by MediaBridge computer M2. M2 is part of anative multicast group and so is able to distribute the packet vianative multicast over the native multicast channel “a.” Accordingly, M2changes the destination and source indicators in the native header to“a” and M2, respectively. Packet 212 is then transmitted throughoutmulticast domain 214 where it is received by M3 and M4. MediaBridgessuch as M5 which haven't joined native multicast group “a” do notreceive packet 212. MediaBridge M4 uses the overlay channel designation“A” to send the packet to client R1 after stripping off the overlayheader “A” so that the packet appears to R1 as a standard packet. M3 andM4 both check the source address and overlay group of packet 212 toensure that it came from an appropriate peer (in this case M2). If not,the packet would have been dropped.

Additional routing of the packet is performed by M3 by the use of asecond native multicasting domain 222 using native multicast address“b.” M3 uses native multicast group “b” by specifying the destination ofpacket 220 (having the same payload as packet 212) as “b.”Thus, multipledifferent native multicast groups can be used to distribute the sameoverlay channel. Packet 220 is distributed through domain 222 via nativemulticast channel “b” to be received by M6 and other possibleMediaBridges, routers, servers, computers, etc. (not shown) that aresubscribed to native multicast channel “b.” M6, similar to M4'soperation, uses the overlay channel designation “A” to determine thatthe packet should be sent to R2 and R3. M6 first strips off the overlaychannel information before sending the packet to R2 and R3.

Although the invention has been presented with respect to particularembodiments thereof, these embodiments merely illustrate possibleembodiments of the invention, the scope of which is determined solely bythe appended claims.

What is claimed is:
 1. A router device, in a first region of nativemulticast connectivity, comprising: one or more processors; one or moresequences of instructions, which, when executed by the one or moreprocessors, cause the router device to perform a method comprising:joining a multicast group that is associated with a particular overlaygroup; receiving flow information that describes a traffic flow type forthe particular overlay group; mapping the particular overlay group to atraffic class based, at least in part, on the flow information;receiving a stream of packets that is associated with the multicastgroup; receiving information indicating a guaranteed bandwidthallocation for the stream based, at least in part, on the traffic classmapped to the particular overlay group; transforming the stream based,at least in part, on the guaranteed bandwidth allocation for forwardingat the guaranteed bandwidth to produce a transformed stream; andforwarding the transformed stream to a second router device in a secondregion of native multicast connectivity.
 2. A method comprising; arouter device in a first region of native multicast connectivity joininga multicast group that is associated with a particular overlay group;the router device receiving flow information that describes a trafficflow type for the particular overlay group; mapping the particularoverlay group to a traffic class based, at least in part, on the flowinformation; receiving a stream of packets that is associated with themulticast group; receiving information indicating a guaranteed bandwidthallocation for the stream based, at least in part, on the traffic classmapped to the particular overlay group; transforming the stream based,at least in part, on the guaranteed bandwidth allocation for forwardingat the guaranteed bandwidth to produce a transformed stream; and therouter device forwarding the transformed stream to a second routerdevice in a second region of native multicast connectivity.
 3. One ormore computer-readable non-transitory media storing one or moresequences of instructions, which, when executed by one or moreprocessors, cause: a router device in a first region of native multicastconnectivity joining a multicast group that is associated with aparticular overlay group; the router device receiving flow informationthat describes a traffic flow type for the particular overlay group;mapping the particular overlay group to a traffic class based, at leastin part, on the flow information; receiving a stream of packets that isassociated with the multicast group; receiving information indicating aguaranteed bandwidth allocation for the stream based, at least in part,on the traffic class mapped to the particular overlay group;transforming the stream based, at least in part, on the guaranteedbandwidth allocation for forwarding at the guaranteed bandwidth toproduce a transformed stream; and the router device forwarding thetransformed stream to a second router device in a second region ofnative multicast connectivity.